Temporary assignment of emergency route back number

ABSTRACT

An emergency route back number (ERBN) may be assigned for use in emergency calls. A telecommunication network associated that may be associated with a wireless service provider, may identify an emergency call directed to an emergency number (e.g., 9-1-1) that originated from a device that is not associated with a unique phone number such as a shared line, or a communication that utilizes some other indicator to establish the emergency call (e.g., an email address, or some other identifier). When an emergency call is detected that does not have a dedicated phone number, an ERIIN is assigned to the communication. This ERBN may be reserved for some period of time after the emergency call ends such that emergency contact centers are able to reach callers back in case of dropped calls, fails, and/or additional emergency services that may need to reach the callers directly.

RELATED APPLICATIONS

This application claims the benefit of priority to provisional U.S.patent application Ser. No. 62/985,816, filed on Mar. 5, 2020, andentitled “Temporary Assignment of Emergency Route Back Number”, which isincorporated by reference in entirety.

BACKGROUND

In the case of an emergency, an individual may call a designatedemergency number, such as “9-1-1” in the United States, or if located inother parts of the world a different emergency number. in the UnitedStates and Canada, dialing “9-1-1” from a telephone links the caller toan emergency contact center, which may be referred to as a Public SafetyAnswering Point (PSAP). In many cases, the location and telephone numberof the caller may automatically be identified by the PSAP. In somecases, however, the location and/or telephone number of the caller maynot be determined. For instance, an individual may be calling from adevice that does not have an associated telephone number and/or the usermay be calling from a shared line that uses the same telephone numberregardless of where the users are located. For example, a shared linemay be used by users in Seattle_(;) Austin, as well as other locations.In these scenarios, if the call is disconnected, the PS AP is not ableto call the user back.

BRIEF DESCRIPTION OF THE DRAWINGS

The detailed description is set forth with reference to the accompanyingfigures.

FIG. 1 is a block diagram showing an illustrative environment fortemporary assignment of an emergency route back number (ERBN).

FIGS. 2A and 2B are block diagrams showing illustrative environments forassociating an ERBN.

FIGS. 3A and 3B are block diagrams showing illustrative environments fora Public Safety Answering Point (PSAP) calling back an individual thathas been assigned an ERBN.

FIGS. 4A and 4B are block diagrams showing illustrative environments fora Public Safety Answering Point (PSAP) calling back an individual usinga shared line that has been assigned an ERBN.

FIG. 5 is a block diagram illustrating a system that includes one ormore components for temporary assignment of an emergency route backnumber (ERBN).

FIG. 6 is a flow diagram of an example process that includes temporaryassignment of an emergency route back number (ERBN), according to someimplementations

DETAILED DESCRIPTION

Described herein are techniques and systems for temporarily assigning atelephone number (which may be referred to herein as an “emergency routeback number (ERBN)”) that may be used to call back a user that has madean emergency call. Using techniques described herein, a network, such asa telecommunication network associated with a wireless service provider,may identify a call directed to an emergency contact center (e.g.,9-1-1) (which may be referred to herein as an “emergency calf”) thatoriginated from a device that is not associated with a telephone numberthat does not have a dedicated phone number. As used herein, a“dedicated phone number” is associated with a single device. Forexample, if a user utilizes a number that is not unique to the device,such as a shared line, then that number is not considered a dedicatedphone number.

In some configurations, when an emergency call is identified by thetelecommunications network as originating from a non-dedicated phonenumber (e.g., a shared line), an ERBN is assigned to the communication.The ERBN acts as a dedicated phone number for the device originating thecall for a configurable period of time. By temporarily assigning theERBN, emergency contact centers (e.g., PSAPs) can reach callers back incase of dropped calls, fails, and/or additional emergency services thatmay need to reach the callers directly.

There are many reasons a user may not be associated with a dedicatedphone number that does not uniquely identify the user. For example, theuser may be using a shared line (hunt group or ring group number) thatis used by multiple users, or the user may be using a device that doesnot have an associated telephone number. In some examples, thecommunications may be over the top communications (OTT) that operateover the Internet and may be received from clients can be serviced bydevices such as tablets, desktop and other devices that do not requireSubscriber Identity Modules (SIMs) to function over telecom networks.This means these devices do not have a native dialer.

As such, when an emergency call is received from a device that does nothave a dedicated number, and instead has an alpha numeric calling ID, ashared number, or some other identifier, an ERBN that acts as adedicated phone number may be temporarily assigned. For emergencyservices to handle the emergency call a dedicated. number is utilized sothat emergency services can return calls and utilize the numbers forreference purposes.

When the emergency services receive the incoming emergency call, thetemporarily assigned ERBN may be provided to the emergency contactcenter. The originator of the emergency call may also be informed of theERBN assigned to the device during the call out as the network wouldsupply it back to the client. For example, if the caller is providedwith the ERBN, the caller may provide the ERBN to the emergency serviceswhen requested. In sonic configuration, the ERBN is temporarilyassociated with the caller during the duration of the ongoing call andsome period of time thereafter (e.g., 5 minutes, 10 minutes, 20 minutes,. . . ).

According to some examples, an emergency route back number (ERBN)component associated with the telecommunications system reserves theERBN number until the timer/duration has expired to be used for thisuser. In some instances, the time to reserve the number is not a hardlimit. According to some configurations, the timer starts after anemergency call has ended. In this way, the ERBN remains alive/mapped tothe user making the emergency call in case emergency services need tocontact the caller back again at some point after the emergency call hasterminated.

In some configurations, if the user who has this number reserved/mappedto their profile and their device IDs (Universal Unique Identifier(UUID)) and makes another 911 call; then the timer for the reserved ERBNgets restarted. This timer may restart each time the user calls back outto 911 and/or receives a call back from the PSAP. This is to help tokeep the ERBN alive for the immediate need of the emergency.

If after the expiry of ERBN that was reserved against that device of theuser and the user makes another emergency call the reserved number thatwas previously utilized can be redistributed to that user and or a newnumber can be reserved for that user. In some examples, an ERBN that wasreserved, and is now released, may be put back for use by anotheremergency caller. According to some examples, the ERBN may bere-assigned after some further time period (e.g., when EBRN is put backin a pool of available ERBNs, the ERBN is not re-assigned immediately toanother user). More details are provided below with reference to FIGS.1-6,

FIG. 1 is a block diagram that shows an illustrative environment 100 fortemporary assignment of an emergency route back number (ERBN) and use ofthe ERBN, Referring to FIG. 1, the environment 100 may include a corenetwork 102 and an access network 122 that is associated with a wirelessservice provider. The environment 100 is illustrated in simplified formand may include many more components.

The environment 100 may include nodes 104, such as nodes 104A 104Z,which may also be referred to herein as “cells”. The nodes 104 may bewireless nodes or wired nodes that are coupled to core network 102and/or some other network. The environment 100 may also include one ormore access points 114, one or more gateways 116, and one or moreservice nodes 106. A node, such as a node 104 may handle traffic andsignals between electronic devices, such as the user equipment111.0A-110N, and a core network 102. For example, a node 104 may performthe transcoding of speech channels, allocation of radio channels toelectronic devices, paging, transmission and reception of voice anddata, as well as other functions. A node 104 may include several basetransceiver stations (BTS), each BTS may include a transceiver, antenna,and additional network switch and control equipment that provide anetwork cell for facilitating wireless communication between UEcomputing devices and the core network 102. In some examples, the nodes104 include a gNodeB and/or an eNodeB.

The core network 102 and/or some other component may be responsible forperforming functionality relating to temporary assignment of anemergency route back number (EARN) 120, routing voice communication toother networks, as well as routing data communication to external packetswitched networks, such as the Internet 112. For example, the one ormore service nodes 106 may be a Gateway GPRS Support Node (GGSN) oranother equivalent node. According to some configurations, the one ormore service nodes also include a Policy and Charging Rules Function(PCRF) node that utilized to enforce policy rules of the network. ThePCRF node can be configured to automatically make policy decisions foreach subscriber (e.g., each user equipment (UE) 110 which may also bereferred to herein as “user equipment”) active on the network. Forexample, the PCRF may be utilized to allocate bandwidth of the networkas well as provide different levels of service to different computingdevices on the network. Additionally, some data can be prioritizedwithin the network,

The user equipment 110 are computing devices that can include, but arenot limited to, smart phones, mobile phones, cell phones, tabletcomputers, portable computers, laptop computers, personal digitalassistants (PDAs), electronic book devices, or any other portableelectronic devices that can generate, request, receive, transmit, orexchange voice, video, and/or digital data using a cellular accessnetwork 122, and/or over a Wi-Fi network, or some other type of network.

In some instances, the UE 110 computing devices can be configured tosend and receive data using any wired or wireless protocols. Additionalexamples of the LE 110 include, but are not limited to, smart devicessuch as televisions, music players, or any other electronic appliancesthat can generate, request, receive, transmit, or exchange voice, video,and/or digital data over a network. The UE 110 can further be configuredto establish or receive a communication session, such as a VoLTE, VoNR,VoWifi, or other voice call, a video call, or another sort ofcommunication. Establishment of such sessions can involve communicationclients and Session Initiation Protocol (SIP) clients to communicatewith the telecommunications network.

In some configurations, one or more of the service nodes 106 may beconfigured as one or more application servers that provide support forone more applications, such as application 111 utilized by one or moreuser equipment 110 computing devices. Some example applications include,but are not limited to browser applications, messaging applications,voice applications (e.g., Voice over Internet Protocol “VoIP”applications), video applications, and the like.

While the service nodes 106 are illustrated within the core network 102,one or more other computing devices may be located outside of the corenetwork 102. For example, an application server, or some other server ordevice, may be connected to the core network 102 via one or moreexternal packet switched networks, such as the Internet. In someexamples, one or more computing devices outside of the core network 102may be utilized to perform processing related to utilizing ERBNs.

According to some configurations, a telephony client application, suchas application 111, on the UE 110A may establish data communication withthe network 102 through a data connection to the node 104A. The node104A may be a node that routes a communication wired/wirelessly from theLE 110A through the access network 122 for communication to the corenetwork 102.

When a communication request arrives at the network 102, one or more ofthe service nodes 106 may determine the identity of the originatingcomputing device for the communication (e.g., using a telephone number,IMEI, IMSI, IP address) as well as the identity of the computing devicesto send the communication. According to some configurations, a UE 110Omay connect to the service nodes 106, or some other component such as anapplication server, via the Internet 112. In such instances, the UE 110Omay connect to the Internet 112 via Wi-Fi access point 114. Accordingly,data traffic from the LIE 110O may be routed to the service nodes 106 bythe gateway 116 of the network 102.

In some configurations, a wireless service provider may utilizealternative access vendor (AAV) networks, for example, which utilizeEthernet networks to provide a wired connection, such as wiredconnection 108, to provide at least a portion of backhaul for broadbandcellular services, such as 5G networks. In other examples, the wirelessservice provider may deploy its own wired connections.

In general, a node 104 can be implemented as a variety of technologiesto provide wired and/or wireless access to the network, as discussedherein. In some instances, the nodes 104 can include a 3GPP RAN, such aGSM/EDGE RAN (GERAN), a Universal Terrestrial RAN (UTRAN), an evolvedUTRAN or a New Radio (5G) RAN, or alternatively, a “non-3GPP” RAN, suchas a Wi-Fi RAN, or another type of wireless local area network (WLAN)that is based on the IEEE 802.11 standards. Further, the nodes 104 caninclude any number and type of transceivers and/or base stationsrepresenting any number and type of macrocells, microcells, picocells,or femtocells, for example, with any type or amount of overlappingcoverage or mutually exclusive coverage. The nodes 104 can be associatedwith access network 177.

As shown in FIG. 1, some nodes 104 have no physical (i.e., “wired”) dataconnection to network. In other words, some of the nodes, such as node104B, are not connected to the core network 102 using fiber cabling,copper cabling, and/or some other type of wired connection. The nodes104 that do not have a wired connection may be connected to one or morewired nodes 104, such as node 104A, that does have a wired connection tothe core network 102. A wired node utilizes fiber, or other wired. dataconnections, to connect to the core network 102. As shown, wired node104A connects to the core network via an Ethernet connection 108 via afiber optic, coaxial, or other high speed wired data connection. A wirednode 104, such as node 104A, could also be connected by a coaxial, T1,T3. or other suitable high-speed connection to the core network 102. Insome configurations, mesh networking technology can be used to connectdifferent nodes 104 within the access network 122. GeographicInformation Services (GIS) and other terrain and location informationsystems can be used to determine nodes to provide a connection betweenone or more non-wired nodes and a network 102.

In some instances, the environment 100 can further include one or moreservers, including service nodes 106, to facilitate communications byand between the various devices in the environment 100 and performoperations relating to assignment of ERBNs. That is, environment 100 caninclude any computing devices implementing various aspects of one ormore of second, third, fourth generation, and fifth generation (2G, 3G,4G, and 5G) cellular-wireless access technologies, which may becross-compatible and may operate collectively to provide datacommunication services. Global Systems for Mobile (GSM) is an example of2G telecommunications technologies; Universal Mobile TelecommunicationsSystem (UMTS) is an example of 3G telecommunications technologies; andLong-Tenn Evolution (LTE), including LTE Advanced, Evolved High-SpeedPacket Access (HSPA+) are examples of 4G, and 5G NR is an example of 5Gtelecommunications technologies. Thus, the environment 100 may implementGSM, UNITS, LTE/LTE Advanced, and/or 5G NR telecommunicationstechnologies.

The environment 100 may include, but is not limited to, a combinationof: base transceiver stations BTSs (e.g., NodeBs, Enhanced-NodeBs,gNodeBs), Radio Network Controllers (RNCs), serving GPRS support nodes(SGSNs), gateway GPRS support nodes (GGSNs), proxies, a mobile switchingcenter (MSC), a mobility management entity (MME), a serving gateway(SGW), a packet data network (PDN) gateway (PGW), an evolved packet datagateway (e-PDG), an Internet Protocol (IP) Multimedia Subsystem (IMS),or any other data traffic control entity configured to communicateand/or route data packets between the UE 110, the nodes 104, and one ormore endpoints of the network (e.g., service nodes 106A-106Q, websites,etc.). While FIG. 1 illustrates an example environment 100, it isunderstood in the context of this document, that the techniquesdiscussed herein may also be implemented in other networkingtechnologies.

The access network 122 can be any sort of access network, such as a GSMor UMTS network. The access network 122 can include any aspects of oneor more of second, third, fourth generation, and fifth generation (2G,3G, 4G, and 5G) cellular-wireless access technologies. The accessnetwork 122 can also be referred to as a universal terrestrial radionetwork (UTRAN) or a GSM EDGE radio access network (GE RAN) and caninclude one or base stations, as well as a radio network controller(RNC). As briefly discussed above, a network, such as an access network122 associated with a wireless telecommunication service provider,

As illustrated, the one or more service nodes 106 includes an emergencyroute back number (ERBN) component 118 configured to perform operationsrelating to temporary assignment of an emergency route back number(ERBN) 120. In the example illustrated in FIG. I, the UE 110A initiallyconnects to node 104A and the UE 110 does not have a dedicated number(e.g., an e.164 number) and is making an emergency call (e.g., 9-1-1).An e.164 number follows the international telephone numbering plan thatensures that each device on the public switched telephone network (PSTN)has globally unique number. This e.164 number allows phone calls andtext messages to be correctly routed to individual phones in differentcountries. In the current example, the emergency route back numbercomponent 118 may temporarily assign an ERBN 120 to the user equipment110A that is associated with the user making the emergency call.

According to some configurations, the emergency route back numbercomponent 118 utilizes a pool of ERBNs 120 when temporarily assigning anERBN 120 to the emergency caller. For example, using techniquesdescribed herein, a network, such as a telecommunication networkassociated with a wireless service provider, may identify a calldirected to an emergency number (e.g., 9-1-1) that originated from adevice that is not associated with a dedicated phone number. In someconfigurations, when an emergency call is detected that originates froma device that does not have a dedicated phone number, such as UE 110Athat does not have a dedicated e.164 number, the ERBN component 118 mayassign an ERBN, such as ERBN 120A, to the device. In some examples, theERBN component 118 selects the ERBN 120A from a pool of available ERBNs120. In other examples, the ERBN component 118 may generate a uniqueERBN.

After assigning the ERBN number, the ERBN may be provided and utilizedby the emergency service as a dedicated number that is associated withthe user equipment 110 originating the call. The originator of theemergency call may also be informed of the ERBN by the ERBN component118. In this way, the user of UE 110A may provide the ERBN to emergencyservice personnel when requested. In some configurations, the ERBN istemporarily associated with the caller utilizing user equipment 110Aduring the duration of the ongoing call and some period of timethereafter (e.g., 5 minutes, 10 minutes, 20 minutes, . . . ).

An ERBN component 118 associated with the telecommunications systemreserves the ERBN number 120A until the timer/duration has expired to beused for this user. In some examples, the time to reserve the number isnot a hard limit. According to some configurations, the timer is startedby the ERBN component 118 after an emergency call has ended. In thisway, the ERBN 120A remains alive/mapped to the user making the emergencycall in case emergency services need to contact the caller back again.In some configurations, if the user who has this number reserved/mappedto their profile and their device IDs (Universal Unique Identifier(UUID)) and makes another 911 call; then the timer for the reserved ERBNgets restarted. This timer would restart each time they call back out to911 and or receive a call back. This is to help to keep the ERBN alivefor the immediate need of the emergency.

If after the expiry of ERBN that was reserved against the UE 110A, andthe user makes another emergency call, the reserved ERBN that waspreviously utilized can be redistributed to that user and or a newnumber can be reserved for that user. In some examples, an f:R13N thatwas reserved, and is now released, may be put back for use by anotheremergency caller. According to some examples, the ERBN may bere-assigned after some further time period (e.g., when EBRN is put backin a pool of available ERBNs, the ERBN is not re-assigned immediately toanother user). More details are provided below with regard to FIGS. 2-6.

FIGS. 2A and 2B are block diagrams showing illustrative environments 200and 250 for associating an ERBN, As discussed above, a client 202. suchas UE 110A, may not have a dedicated el64, and instead utilizes an alphanumeric calling ID or a shared number. For emergency services, such asPSAP 210, to handle and emergency call, a dedicated number is utilizedso that emergency services can return calls and utilize the numbers forreference purposes. As illustrated, FIG. 2A shows an example of over thetop client's 202A-202C route towards an associated signaling/mediagateway 204A-204C and then communicate to a server, such as SIP server206, that may generate and map/reserve the ERBN for that callerassociated with a client.

According to some configurations, the SIP server 206 may communicatewith application servers, such as one or more service nodes 106, thatmay utilize a device ID(s) reference to map and hold/reserve an ERBN 120in order for an emergency service to call/reach back to reach the userthat originated the emergency call.

As discussed above, when a client 202, such as client 202 makes a call212 to emergency services, the server 206 may associate an ERBN 120 withthe device of the client 202A, in some examples, the ERBN component 118of server 206, or located at some other location, obtains an availableERBN 120 from a pool of ERBNs 120. In some configurations, the server206, or some other device or component, may also set a timer for aconfigurable period of time such that the ERBN assigned to the client202A that does not have a dedicated number can be reached in case acommunication to the PSAP 210 is dropped and/or the user needs to becontacted. According to some examples, the server 206 starts the timerafter the call has been ended.

When a PSAP 210 associated with the emergency services receives theincoming emergency call, the temporarily assigned ERBN which has beenassociated with client 202A may be presented via a display, audibly, orsome other user interface) to the emergency services personnel handlingthe call.

The originator of the emergency call, such as client 202A, may also heinformed of the assigned ERBN 120 by the ERBN component 118, or someother component or device. The server 206, or some other device orcomponent, may continue to reserve the ERBN for some period of time. Forexample, until the timer/duration has expired for the particularemergency call (e.g.. 10, 20, 40 mins, which can be modified to belonger/shorter not a hard limit). The timer may start during the call,after the call, or at some other time in order such that the ERBN 120stays alive/mapped to that user in case emergency services need tocontact the caller back again. If the user who has this ERBNreserved/mapped to their profile and their device IDs (UUID) and makesanother 911 call; then the timer for the reserved. ERBN may restart.This timer may be restarted each time they call back out to 911 and orreceive a call back. This is to help to keep the number alive for theimmediate need of the emergency.

If after the expiry of the ERBN and a client 202 makes another emergencycall the reserved ERBN that was previously utilized can be redistributedby the ERBN component 118 of server 206 to that user or a new number canbe reserved for that user. In some examples, there is a period of time(i.e., a grace period) that restricts distributing a recently reservednumber for at least some period of time when the ERBN is put back in thepool.

Referring to FIG. 2B, a client 202A is utilizing an electronic message,such as a text message 214 to contact PSAP 210. When the PSAP 210associated with the emergency services receives the incoming textmessage, the ERBN associated with client 202A may be presented as data216. The client 202A that originated the emergency message may also beprovided the assigned ERBN. As discussed, in some examples, the ERBN istemporarily associated with a. device of the client 202A by the server206 during the duration of the ongoing conversation (messaging).

As illustrated, a gateway, such as gateway 202A may request the ERBNfrom server 206. The gateway 202A may be connected to an InterconnectionBorder Control Function (IBCF) 216. The IBCF 216 may be used as agateway to external networks, such as a network associated with theemergency services. A text control center (TCC) 224 may be connected tothe IBCF 220 that may be configured to receive messages, such as but notlimited to short message short message service (SMS) messages,multimedia messaging service NMS) messages, and possibly other type ofmessages. The ERBN and data of the electronic message 214 may be sent tohe PSAP 210 via the MCF 220 and the TCC 224. The Gateway Mobile LocationCenter (GMLC) 222 may be configured to provide location-based services(LBS). For example, the GMLC 222 may be configured to provide a locationof the client 202A originating the emergency text to the emergencyservices.

The server 206 and/or some other device or component may continue toreserve the ERBN for the client 202A until the timer/duration hasexpired (e.g., 10, 20, 40 mins, which can be modified to belonger/shorter not a hard limit). The timer may be started by the server206 after the initial message and first response has ended to keep thenumber alive/mapped to that user in case the emergency services need tocontact the user back again. if the user who has this numberreserved/mapped to their profile and their device IDs (UUID) and makesanother 911 call or message; then the timer for the reserved ERBN may berestarted. This timer may be restarted each time they reply back out to911 and/or receive a direct message back from the PSAP 202, This is tohelp to keep the number alive for the immediate need of the emergency.

If after the expiry of that number that was reserved against that userand the subscriber makes another emergency text, the reserved numberthat was previously utilized can be redistributed to that user and or anew number can be reserved for that user. In some cases, there is agrace period of this number and when the number is put back in the poolit is not re-assigned immediately to another user.

FIG. 3A and 3B are block diagrams showing illustrative environments 300and 350 for associating an ERBN with a device that does not have adedicated phone number. As illustrated, the environment 300 shows a callflow that originates from a client 202 and flows to the PSAP 210 and theenvironment 350 shows a message flows that originates from a client 202and flows to the PSAP 210. FIGS. 3A and 3B include more detail ascompared to FIGS. 2A and 2B.

As illustrated in FIG. 3A, environment 300 includes Emergency CallSession Control Function E-CSCF) 302 that is configured to be utilizedfor emergency calls between clients 202 and PSAP 210. When communicatingwith the PSAP 210, the E-CSCE 302 is configured to replace emergencyidentifiers with the actual PSAP Session Initiation Protocol (SIP)Uniform Resource Identifier (URI) such that communications from theclient 202. reach the PSAP 210. In some examples, if locationinformation for the client 202, such as client 202A was not provided,the E-CSCF 302 will query the GMLC 222 that may obtain the registeredlocation of the client 202 from the data store 306. The E,-CSCR 302 maythen communicate with the outbound SIP server 304 that connects theemergency call to the PSAP 210. FIG. 3B is similar to FIG. 2B butincludes GMLC 222 coupled to data store 306 that may configured toretrieve location information for client 202A, and other clients 202.

FIGS. 4A and 4B are block diagrams showing illustrative environments 400and 450 for flows for a Public Safety Answering Point (PSAP) 210 callingback or messaging back an individual using a shared line that has beenassigned an ERBN. As illustrated in environment 400, a PSAP 210associated with the PSAB 210 calls back a client 202A that had an ERBNmapped to it in response to making an emergency call. In the currentexample, users in a shared group that may be associated with the callerthat made the emergency call will not receive the call back from thePSAP 210. Instead, the specific user (e.g., client 202A) that made thecall will receive the call back on the device utilized to contact thePSAP 210. According to some configurations, the inbound peering server404 receives the call data 402 from PSAP 210 that communicates withserver 206. As discussed above, the hosted SIP server 206 may store anidentifier of the device/user that made the emergency call and create abinding with the ERIN such that when receiving the call from PSAP 210,the call may be routed to client 202A.

FIG. 4B illustrates the PSAP 210 communicating with the client 202A viaelectronic message 406. As illustrated, the I-BCSF 220 may communicatethe message 406 with a message service, such as short messaging service(SMS) 408. SMS 408 communicates with the Interrogating—CSCF (I-CSCF)and/or the Serving CSCF (S-CSCF). Generally, the I-CSCF is responsiblefor routing of SIP messages to the appropriate S-CSCF (Serving CSCF) fora given client 202. Routing SIP requests arriving from other SIPnetworks may also be performed by the I-CSCF. The S-CSCF is a SIP serverthat is configured to perform session control. A combination of the I-CSCE and the S-CSCF make up the I/S-CSCF 410. The I/S-CSCE 410communicates with rich messaging service (RMS) 412 that communicates themessage 406 from PSAP 210 to client 202A.

FIG. 5 is a block diagram illustrating a system 500 that includes one ormore components for temporary assignment of an emergency route backnumber (ERBN) according to some implementations. The system 500 includesa terminal 502, which can represent a UE 110, or another computingdevice, coupled to a server 504, via a network 506. The server 504 canrepresent a computing device, such as one or more of the servers withinthe network 102 and/or access network 122., and/or some other computingdevice. The network 506 can represent network 102 and/or access network122, or some other network.

The network 506 can include one or more networks, such as a cellularnetwork 508 and a data network 510. The network 506 can include one ormore core network(s) connected to terminal(s) via one or more accessnetwork(s). Example access networks include LTE, WIFI, GSM Enhanced DataRates for GSM Evolution (EDGE) Radio Access Network (GERAN), UTRAN, andother cellular access networks. Message transmission, reception,fallback, and deduplication as described herein can be performed, e.g.,via 5G, 4G, 5G, WIFI, or other networks,

The cellular network 508 can provide wide-area wireless coverage using atechnology such as GSM, Code Division Multiple Access (CDMA), UMTS, LTE,NR, or the like. Example networks include Time Division Multiple Access(TDMA), Evolution-Data Optimized (ENDO), Advanced LTE (LTE+), GenericAccess Network (GAN), Unlicensed Mobile Access (UMA), OrthogonalFrequency Division Multiple Access (OFDM), GPRS, EDGE, Advanced MobilePhone System (AMPS), High Speed Packet Access (HSPA), evolved HSPA(HSPA+), VoIP, VoLTE, IEEE 802.1x protocols, wireless microwave access(WIMAX), WIFI, and/or any future IP-based network technology orevolution of an existing IP-based network technology. Communicationsbetween the server 504 and terminals such as the terminal 502 canadditionally or alternatively be performed using other technologies,such as wired (Plain Old Telephone Service, POTS, or PSTN lines),optical (e.g., Synchronous Optical NETwork, SONET) technologies, and thelike.

The data network 510 can include various types of networks fortransmitting and receiving data (e.g., data packets), including networksusing technologies such as IEEE 802.15.1 (“BLUETOOTH”), AsynchronousTransfer Mode (ATM), WIMAX, and other network technologies, e.g.,configured to transport IP packets. In some examples, the server 504includes or is communicatively connected with an IWF or other devicebridging networks, es., LIE, 5G, and POTS networks. In some examples,the server 504 can bridge SS7 traffic from the PSTN into the network506, e.g., permitting PSTN customers to place calls to cellularcustomers and vice versa.

In some examples, the cellular network 508 and the data nets pork 510can carry voice or data. For example, the data network 510 can carryvoice traffic using VoIP or other technologies as well as data traffic,or the cellular network 508 can carry data packets using HSPA, or othertechnologies as well as voice traffic. Some cellular networks 508 carryboth data and voice in a PS format. For example, many LTE networks carryvoice traffic in data packets according to the VoLTE standard. Variousexamples herein provide origination and termination of, e.g.,carrier-grade voice calls on, e.g., networks 506 using CS transports ormixed VoLTE/3G transports, or on terminals 302 including OEM handsetsand non-OEM handsets.

The terminal 502 can be or include a wireless phone, a wired phone, atablet computer, a laptop computer, a wristwatch, or other type ofterminal. The terminal 502 can include one or more processors 512, e.g.,one or more processor devices such as microprocessors, microcontrollers,field-programmable gate arrays (FPGAs), application-specific integratedcircuits (ASICs), programmable logic devices (PLDs), programmable logicarrays (PLAs), programmable array logic devices (PALs), or digitalsignal processors (DSPs), and one or more computer readable media (CRM)514, such as memory (e.g., random access memory (RAM), solid statedrives (SSDs), or the like), disk drives (e.g., platter-based harddrives), another type of computer-readable media, or any combinationthereof. The CRM or other memory of terminal 502 can hold a datastore,e.g., an SQL or NoSQL database, a graph database, a BLOB, or anothercollection of data. The terminal 502 can further include a userinterface (UI) 516, e.g., including an electronic display device, aspeaker, a vibration unit, a touchscreen, or other devices forpresenting information to a user and receiving commands from the user.The terminal 502 can further include one or more network interface(s)518 configured to selectively communicate (wired or wirelessly) via thenetwork 506, e.g., via an access network 122.

The CRM 514 can be used to store data and to store instructions that areexecutable by the processors 512 to perform various functions asdescribed herein. The CRM 514 can store various types of instructionsand data, such as an operating system, device drivers, etc. Theprocessor-executable instructions can be executed by the processors 512to perform the various functions described herein.

The CRM 514 can be or include computer-readable storage media.Computer-readable storage media include, but are not limited to, RAM,ROM, EEPROM, flash memory or other memory technology, CD-ROM, digitalversatile discs (DVD) or other optical storage, magnetic cassettes,magnetic tape, magnetic disk storage or other magnetic storage devices,or any other tangible, non-transitory medium which can be used to storethe desired information and which can be accessed by the processors 512.Tangible computer-readable media can include volatile and nonvolatile,removable and non-removable media implemented in any method ortechnology for storage of information, such as computer readableinstructions, data structures, program components, or other data.

The CRM 514 can include processor-executable instructions of anapplication 520. The CRM 514 can store information 522 identifying theterminal 502. The information 522 can include, e.g., an IMEI, an IMSIidentifying the subscriber using terminal 502, or other informationdiscussed above. The CRM 514 can additionally or alternatively storecredentials (omitted for brevity) used for access, e.g., to IMS or RCSservices.

The server 504 can include one or more processors 528 and one or moreCRM 530. The CRM 530 can be used to store processor-executableinstructions of a data processing component 532, an emergency route backnumber component 534 which may be emergency route back number component118, a network configuration component 536, as well as one or snoreother components 538. The processor-executable instructions can beexecuted by the one or more processors 528 to perform various functionsdescribed herein.

In some examples, server 504 can communicate with is communicativelyconnectable with) terminal 502 or other devices via one or morecommunications interface(s) 540, e.g., network transceivers for wired orwireless networks, or memory interfaces. Example communicationsinterface(s) 540 can include ETHERNET or FIBRE CHANNEL transceivers,WIFI radios, or DDR memory-bus controllers((e.g., for DMA transfers to anetwork card installed in a physical server 504).

In some examples, processor 512 and, if required, CRM 514, are referredto for brevity herein as a “control unit.” For example, a control unitcan include a CPU or DSP and instructions executable by that CPU or DSPto cause that CPU or DSP to perform functions described herein.Additionally, or alternatively, a control unit can include an ASIC,FPGA, or other logic device(s) wired (physically or via blown fuses orlogic-cell configuration data) to perform functions described herein.Other examples of control units can include processor 528 and, ifrequired, CRM 530.

EXAMPLE PROCESS

FIG. 6 illustrates an example process. The process is illustrated as alogical flow graph, each operation of which represents a sequence ofoperations that can be implemented in hardware, software, or acombination thereof. In the context of software, the operationsrepresent computer-executable instructions stored on one or morecomputer-readable storage media that, when executed by one or moreprocessors, perform the recited operations. Generally,computer-executable instructions include routines, programs, objects,components, data structures, and the like that perform particularfunctions or implement particular abstract data types. The order inwhich the operations are described is not intended to be construed as alimitation, and any number of the described operations can be combinedin any order and/or in parallel to implement the processes.

FIG. 6 illustrates an example process for includes temporary assignmentof an emergency route back number (ERBN). The process includes, at 602,receiving an emergency call. As discussed above, the emergency call maybe received by a telecommunication network, such as access network 122,core network 102, associated with a wireless service provider.

At 604, a determination is made that the emergency call was made from adevice that is associated with a unique telephone number that is uniqueto the device/caller. As discussed above, the emergency call may be madefrom a device, such as UE 110A, that is not associated with a dedicatedphone number that is unique to the user and/or the device, such as ashared line, or a communication that utilizes some other indicator toestablish the emergency call (e.g., an email address, or sonic otheridentifier). In some examples, a gateway 204 coupled to the UE 110 isconfigured to determine that the LTE 110A has a non-unique number.

At 606, an ERBN is identified/generated. As discussed above, theemergency route back number component 118 may obtain an ERBN 120 from apool of available ERBNs or generate or identify an EKBN using some othertechnique or mechanism. According to some configurations, a SIP server206 obtains/generates an ERBN for the UE 110A.

At 608, the ERBN is assigned. As discussed above, the ERBN component 118may associate the identified ERBN 120 with the device and user thatoriginated the call. According to some configurations, the server 206stores a mapping between the LE 110A and the temporary ERBN associatedwith the UE 110A. The server 206 may provide the ERBN for LE 110A to thePSAP 210 and/or the client 202A that is associated with the UE 110A.

At 610, the user associated with the UE 110A is connected with the PSAP210 and the emergency call is in progress. As discussed above, the ERBNthat has been associated with the UE 110A making the emergency call isprovided by the server 206 to the PSAP 210.

At decision block 612, a determination is made as to whether theemergency call has ended. When the emergency call has not ended, theprocess returns to 610. When the emergency call has ended, the processmoves to 614.

At 614, the ERBN is reserved for some period of time after the emergencycall has ended. As discussed above, the ERBN component 118 may reservethe ERBN number after an emergency call has ended for some period oftime. According to some configurations, the ERBN component 118 mayutilize a timer to determine when to release the ERBN. in this way, theERBN remains alive/mapped to the user making the emergency call in caseemergency services need to contact the caller back again. In someconfigurations, if the user who has this number reserved/mapped to theirprofile and their device IDs (Universal Unique Identifier (UUID)) andmakes another 911 call; then the timer for the reserved ERBN getsrestarted, This timer would restart each time they call back out to 911and or receive a call back. This is to help to keep the ERBN alive forthe immediate need of the emergency.

At 616, the ERBN is released. As discussed above, the ERBN component 118and/or the server 206 may release the ERBN such that it may be utilizedby another device and/or the same UE 110 for another emergency call,

Although the subject matter has been described in language specific tostructural features and/or methodological acts, it is to be understoodthat the subject matter described in this disclosure is not necessarilylimited to any of the specific features or acts described. Rather, thespecific features and acts are disclosed as examples and embodiments ofthe present disclosure.

What is claimed is:
 1. A system comprising: one or more processors; amemory; and one or snore components stored in the memory and executableby the one or more processors to perform operations comprising:receiving, from a user equipment (UE) associated with a wirelesstelecommunications network, a request to establish an emergency callwith a Public Safety Answering Point (PSAP); identifying that the UE isassociated with a non-unique telephone number; temporarily associatingan emergency route back number (ERBN) with the UE during the emergencycall and at least for at least a period of time after the emergency callhas ended; and removing the association of the ERBN with the UE upon anoccurrence of one or more events after the emergency call has ended. 2.The system of claim 1, wherein the identifying that the UE is associatedwith a non-unique telephone number comprises determining that the UE isassociated with one or more of a shared line, and a hunt group.
 3. Thesystem of claim 1, wherein associating the ERBN with the UE, comprisesobtaining the ERBN from a group of available ERBNs
 4. The system ofclaim 1, further comprising providing the ERBN to one or more of thePSAP and the UE.
 5. The system of claim 1, further comprisingdetermining that the emergency call has ended and maintaining theassociation of the ERBN with the UE for the period of time.
 6. Thesystem of claim 5, wherein removing the association of the ERBN with theUE upon the occurrence of the one or more events comprises determiningthat the period of time has passed after the emergency call has endedand removing the association.
 7. The system of claim 1, wherein removingthe association of the ERBN with the UE comprises returning the ERBN toa pool of ERBNs that are available for assignment by a component withinthe wireless telecommunications network.
 8. A method comprisingreceiving, from a user equipment (UE) associated with a wirelesstelecommunications network, a request to establish an emergency call;temporarily associating an emergency route back number (ERBN) with theUE during the emergency call and at least for at least a period of timeafter the emergency call has ended; and removing the association of theERBN with the UE upon an occurrence of one or more events after theemergency call has ended.
 9. The method of claim 8, further comprisingidentifying that the UE is associated with a non-unique telephonenumber.
 10. The method of claim 8, wherein associating the ERBN with theUE, comprises one or more of generating the ERBN and obtaining the ERBNfrom a group of available ERBNs.
 11. The method of claim 8, furthercomprising providing the ERBN to one or more of a PSAP and the UE. 12.The method of claim 8, further comprising determining that the emergencycall has ended and maintaining the association of the ERBN with the UEfor the period of time.
 13. The method of claim 12, wherein removing theassociation of the ERBN with the UE upon the occurrence of the one ormore events comprises determining that the period of time has passed andremoving the association.
 14. The method of claim 8, wherein removingthe association of the ERBN with the UE comprises returning the ERBN toa pool of ERBNs that are available for assignment by a component withinthe wireless telecommunications network
 15. A device comprising: one ormore processors; a memory; and one or more components stored in thememory and executable by the one or more processors to performoperations comprising: receiving a request to associate an emergencyroute back number (ERBN) with a user equipment (UE) that is associatedwith a wireless telecommunications network; obtaining the ERBN; andcausing the ERBN to be associated with the UE for a period of time thatincludes a first time associated with an emergency call and a secondtime that extends after the emergency call has ended.
 16. The device ofclaim 15, further comprising removing the association of the ERBN at anexpiration of the second time.
 17. The device of claim
 15. wherein therequest is received from a gateway coupled to the UE and wherein theERBN is utilized for an emergency call that includes the LTE and aPublic Safety Answering Point (PSAP).
 18. The device of claim 15,further comprising causing the ERBN to be provided to one or more of thePSAP and the
 19. The device of claim 15, wherein the UE Is associatedwith one or more of a shared line or a hunt group.
 20. The device ofclaim 15, wherein obtaining the ERBN comprises obtaining the ERBN from agroup of available ERBNs.